Self-organized power and energy control and management systems and methods

ABSTRACT

Systems and methods self-organize a multifunctional power and energy control and management system by integrating multiple backplane based modules through module descriptions. Dynamic data table structures may be configured based on information provides with the module descriptions and provide for improved data accessing, storing, and updating.

CROSS-REFERENCE TO RELATED APPLICATIONS

Not applicable.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

BACKGROUND OF THE INVENTION

The present invention relates generally to power and energy relatedcontrol and monitoring functions and, more particularly, to systems andmethods for building a multifunctional power and energy control andmanagement system by integrating multiple backplane based modulesthrough module descriptions.

Often, for power and energy related control and monitoring applications,there are a variety of application specific requirements that addcomplexity and cost to the application specific systems, typically basedon the types and amounts of data gathered. Examples of power and energyrelated control and monitoring applications include power monitoring,HVAC, line synchronization, motor protectors, transformer protectors,and application specific devices. Using power monitoring as an example,unfavorable events, such as voltage sags, swells, or transient eventscan occur randomly any location within a facility's distribution system.These events can damage or reduce the life of equipment connected to thedistribution system, they can cause connected equipment to malfunction,or even worse, cause harm to personnel. A power monitoring system isused to detect and capture typically large amounts of data related tothese events when they occur. The captured data can then be examined andanalyzed in an effort to understand the event and determine the cause ofthe event. Potential corrective actions can be identified andimplemented to reduce or eliminate a reoccurrence of the event.

Prior known systems for power and energy related control and monitoringapplications have several drawbacks. For example, when these prior knownsystems are configured for first time use, or when additional modulesare added to the system, these systems are not able to “self organize,”meaning they need user intervention prior to and during initializationand revisions in order to properly configure the system to functionaccording to the desired application. In addition, prior known systemshave not adequately addressed the need for greater data storage whilecombining greater data storage with improved data access speeds.

In order to configure these known systems prior to use, the end usermust use configuration software. Some of these prior known systemsinclude multiple modules assembled together, requiring the user tomanipulate the configuration software to indicate what modules are partof the system, and then the configuration software, based upon the userinput, configures the system as input to the configuration software bythe user. If an error in the configuration of the system is made by theuser, the system may not recognize the error because the system would beconfigured based upon the user input.

Additionally, these systems typically access and store large amounts ofpower and energy related data for later review and analysis. These priortypes of systems frequently incorporate a commercial or free embeddeddatabase to perform data access, storage, and updates. Because thesedatabases are general purpose, they are rarely if ever suitable for theever increasing large amounts of power and energy related data that isaccessed, stored, and frequently updated.

It would, therefore, be desirable to have systems and methods thatself-organize a multifunctional power and energy control and managementsystem by integrating multiple backplane based modules through moduledescriptions. A dynamic data structure configured with moduledescription information improves data access, storage, and updating.

BRIEF SUMMARY OF THE INVENTION

The present embodiments overcomes the aforementioned drawbacks of theprevious strategies by providing systems and methods that are adapted toself-organize a multifunctional power and energy control and managementsystem by integrating multiple backplane based modules through moduledescriptions without the need for a user to configure the system byinputting system information into configuration software. A dynamic datastructure may be configured based on the module descriptions to improvedata access, storage and updating.

In accordance with one aspect of the invention, a system is provided.The system comprises a backplane assembly and at least one functionalmodule coupled to the backplane assembly. The functional module isadapted to receive process related data, and includes a unique moduledescription, the module description including information about datastructures and control logic of the at least one functional module. Aprimary module is also coupled to the backplane assembly, with theprimary module including a description parser adapted to receive andinterpret the at least one module description upon self-organization ofthe system and to create a dynamic data table structure.

In accordance with another aspect of the invention, a power and energycontrol and management system is provided. The power and energy controland management system comprises a backplane assembly with a functionalmodule coupled to the backplane assembly. The functional module includesat least one internal data table and a unique module description, theunique module description including information about the internal datatable parameters and external data table parameters of the functionalmodule. The system also includes a primary module coupled to thebackplane assembly, the primary module including a description parseradapted to receive and interpret the internal data table parameters andthe external data table parameters of the functional module uponself-organization of the system, and to create a dynamic data tablestructure including at least one external data table, the at least oneexternal data table being dynamically created based on the external datatable structures of the functional module.

In accordance with yet another aspect of the invention, a method ofself-organizing a power and energy control and management system isprovided. The method comprising steps including inputting into adescription generator tool information about a functional module, theinformation comprising information about internal data table structuresand external data table structures; creating a module descriptionspecific to the functional module by compiling the information inputinto the description generator tool; saving the module description inmemory in the functional module; and self-organizing the system by i)sending the module description across a backplane assembly to a primarymodule, the primary module adapted to receive the module description;ii) using a description parser to create dynamic data table structuresbased on the module description; and iii) establishing an I/O connectionbetween the primary module and the functional module.

To the accomplishment of the foregoing and related ends, theembodiments, then, comprise the features hereinafter fully described.The following description and the annexed drawings set forth in detailcertain illustrative aspects of the invention. However, these aspectsare indicative of but a few of the various ways in which the principlesof the invention can be employed. Other aspects, advantages and novelfeatures of the invention will become apparent from the followingdetailed description of the invention when considered in conjunctionwith the drawings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The embodiments will hereafter be described with reference to theaccompanying drawings, wherein like reference numerals denote likeelements, and:

FIG. 1 is a schematic diagram of a power and energy control andmanagement system in accordance with the present embodiments;

FIG. 2 is a block diagram of the power and energy control and managementsystem of FIG. 1, showing how the system self-organizes and buildscommunications with the functional modules through their moduledescriptions;

FIG. 3 is a block diagram showing a dynamic data structure of a powerand energy control and management system in accordance with the presentembodiments;

FIG. 4 is a block diagram of a producer/consumer communication modelusable with the present embodiments;

FIG. 5 is a flow chart showing the steps of creating a moduledescription according to an embodiment of the invention;

FIG. 6 is a block diagram showing an embodiment of a descriptiongenerator tool kit; and

FIG. 7 is a flow chart showing the steps of self-organizing a power andenergy control and management system according to an embodiment of theinvention.

DETAILED DESCRIPTION OF THE INVENTION

The various aspects of the present embodiments will be described inconnection with various power and energy related control and managementsystems and methods. That is because the features and advantages thatarise due to the embodiments are well suited to this purpose. For thisreason, the systems and methods will be described in the context of asystem configured for a power monitoring application. Still, it shouldbe appreciated that the various aspects of the invention can be appliedto achieve other objectives as well. For example, the systems andmethods of the present invention may include systems adapted for otherapplications such as HVAC, line synchronization, motor protectors,transformer protectors, application specific devices, and anycombination, as non-limiting examples, for the same or similar purposes.

A flexible and multifunctional product platform is disclosed and can beadapted to meet any of the application requirements mentioned herein.This platform provides users with a flexible system able to lowerdevelopment and maintenance costs, while providing improved systems andmethods to implement other new power and energy control and managementapplication functions.

In order to implement the system and methods, a number of technicalproblems need to be solved. For example, it would be desirable toprovide a user friendly and efficient way to self-organize amultifunctional power and energy control and management system withoutrequiring the system user to use configuration software, and to add newmodules to the system with little or no firmware changes to the existingsystem modules. In addition, the large amounts of power and energy datarequire an improved access mechanism to provide faster data updating andaccessing.

The disclosure herein provides systems and methods adapted toself-organize a multifunctional power and energy control and managementsystem that overcome the technical problems above by integratingmultiple backplane based modules through individual module descriptions.Incorporating dynamic data table structures that may be configured basedon the module descriptions provides for improved data accessing,storing, and updating.

Referring now to FIG. 1, exemplary power and energy control andmanagement system 10 is shown that overcomes the drawbacks addressedabove. The system 10 may comprise a primary module 12 and multiplefunctional modules, including functional module 1 (14), functionalmodule 2 (16), power supply module 18, and up to functional module n(20), where n may be any maximum number of modules the system maysupport. FIG. 1 shows four functional modules 14, 16, 18, and 20,although more or less may be incorporated into the system 10. Themodules exchange data through a backplane assembly 22 and may receivepower across the backplane assembly 22 from the power supply module 18.

Each of the components will now described in further detail. It is to beappreciated that the system 10 may include alternative configurations aswell. For example, one or more of the modules may be combined, and/orfeatures or functions described for one module may be located orincorporated on a different module. Processors, memory, andcommunications may be located in or on one or more of the modules,and/or elsewhere on a network coupled to the system 10. Additionalmodules providing additional system or monitoring related functions mayalso be included.

In the exemplary embodiment shown in FIG. 1, the modular system 10 maycomprise multiple modules coupled to the backplane 22, each of whichperform specific functions. Non-limiting examples of modules that may beused in a power and energy control and management system include theprimary module 12, a power data acquisition module 14, an I/O module 16,and a power supply module 18. The backplane based modular system 10 iswell adapted to configure new systems with different functional modulegroups.

Primary module 12 may include one or more processors 24 and internalmemory 25, and may be configured to be responsible for top level controlof the system 10. The primary module may also be configured to manageits communications 26 to and from the backplane assembly 22. Primarymodule 12 may also include a communications interface 28 including oneor more user accessible communication ports 30, 32, 34 (three are shown,although more or less are contemplated). For example, the communicationports may be configured for a variety of communication protocols,including but not limited to USB, serial, wireless, Bluetooth, EtherNet,DeviceNet, ControlNet, and Ethernet with Device Level Ring (DLR)technology. The DLR technology also supports the IEEE 1588 standard forprecise time synchronization and standardized Quality of Service (QoS)mechanisms to help prioritize data transmission. One or more of thecommunication ports allows the system 10 to be networked to additionalpower and energy control and management systems.

The power supply module 18 may be included and may be adapted to acceptuser input voltage in either VAC and/or VDC, and configure the inputvoltage to a system or output voltage that may then be supplied to thebackplane assembly 22 for distribution to the other modules, e.g.,primary module 12 and functional modules 14, 16, and 20, coupled to thebackplane assembly. The power supply module 18 may be configured tomanage its communications 36 to and from the backplane assembly 22. Itis to be appreciated that both input and output voltages may range fromlow voltage levels to high voltage levels as is well known in the art.It is also to be appreciated that transformers known in the art may alsobe used with high voltage systems. The power supply module 18 may alsobe configured to include standby power, e.g., a standby capacitor orbattery 38, for providing power to the system 10 when user input voltageis temporarily not available.

The backplane assembly 22 may be configured as a local Ethernetbackplane, although other configurations are contemplated, such as aproprietary configuration. Each module coupled to the backplane assembly22 is adapted to draw power, e.g., a system voltage, from the backplaneassembly and communicate with the primary module 12 and the othermodules 14, 16, 18, and 20 across the backplane assembly 22. Inaddition, the backplane assembly 22 may be configured to provideelectrical isolation between modules coupled to the backplane assembly.

Before the very first startup, the primary module 12 knows nothing aboutany of the functional modules in the system 10. In order to communicatewith each functional module, and as part of the self-organizationprocess, the primary module 12 will acquire a unique module description40 from each of the functional modules 14, 16, 18, and 20, and create adynamic data table structure 42 (also known as a linked list) to managethe data received from and transmitted to each of the functional modulesin the system. Each functional module 14, 16, 20 may be configured tomanage its communications 43 to and from the backplane assembly 22. Oneor more functional modules may be adapted to receive process relateddata, processes including but not limited to water, air, gas, electric,and steam.

Each functional module has its own unique embedded module description 40that describes the module parameters, which includes detailedinformation about the data and data structures, including internal datatable parameters 44 and external data table parameters 46, whichdescribes their contents and properties, and the control logic 48 in theparticular functional module (shown in FIG. 3). Each module may have anynumber of parameters, ranging from one to thousands or more, which aregrouped into the data tables. Each functional module has one or more ofits own internal data tables 45 to save real-time data and/orconfiguration parameters. The primary module 12 also has correspondinginternal data tables 45 corresponding to each of the internal datatables from each of the functional modules. For example, the functionalmodule 14 may include a static internal “metering data table” in itsmemory 86, and the primary module 12 desirably includes the sameinternal “metering data table” in its memory 25, which is createddynamically by the primary module 12 according to the module description40 of functional module 14. The internal data tables 45 are used toexchange data among the functional modules and the primary module. Inone embodiment, the internal data tables 45 may be relatively large toachieve a high backplane throughput.

Only the primary module 12 has external data tables 47, which are usedto exchange data with external devices, such as via the network 100. Theexternal data tables 47 are also created dynamically by the primarymodule 12 according to the module description 40 of each functionalmodule. The external data tables 47 may be organized according to theparameter's physical meanings to provide a more friendly and readilyunderstandable user interface. For example, the functional module 14 mayinclude the static internal “metering data table,” which contains valuesof 150 variables (in this example). These variables can be reorganizedinto a few external data tables 47, such as “voltage, current, andfrequency table,” “power data table,” and “energy data table,” asnon-limiting examples.

Referring to FIGS. 1 and 2, and particularly FIG. 2, the primary module12 includes a description parser 50 and a logic engine 52, and uses thedescription parser 50 to create the dynamic data table structures 42 anda parameter list 51 according to the functional module descriptions.Parameters in the parameter list 51 may then be selected by an end useras inputs to predefined logic (e.g., set-point logic, min-max comparisonlogic) in the logic engine 52, or as inputs to custom logic configuredby the end user.

Once the data structures 42 are defined for a particular functionalmodule, the primary module 12 can then exchange data with the functionalmodule. The primary module may also be responsible for communicationwith external devices, such as via the network 100, further describedbelow. The primary module 12 can represent the whole system 10 tocommunicate with the external devices using the external data tables.The primary module 12 may have data logging threads 66 and other threads68 in the memory 25, which may be responsible for executing a variety ofdifferent functions. For example, some threads may be responsible forbackplane communication, some may be responsible for externalcommunications, and others may be responsible for data logging.

In the system run time, the primary module 12 creates I/O connections 56with each of the functional modules to subscribe data (described below)from the functional modules. When any of the parameters of thefunctional modules are changed, the functional module will send the newdata to the primary module 12, and the primary module 12 will update thedynamic data structure 42 with the new data.

FIG. 2 shows an embodiment of how the primary module 12 buildscommunication with each of the functional modules in the system throughthe use of the functional module descriptions 40 and the primarymodule's description parser 50. During the system initialization (theself-organization), the primary module 12 acquires each functionalmodule's embedded description 40. The description parser 50 then useseach functional module's description 40 to create the dynamic data tablestructures 42 for the module based on the module description. The datatable server 58 then opens an I/O connection 56 between the primarymodule 12 and each functional module, thereby allowing the primarymodule 12 to subscribe data from the functional modules (the datapublishers).

Description generation tool kits 60 can be developed and made availablefor users to create module descriptions for new functional modules sothey may be incorporated into the multifunctional system. At the sametime, it is also contemplated that third party vendors may develop andadd their own application specific functions into the system with theuse of the description generation tools.

Referring to FIG. 3, the dynamic data table structure 42 in the primarymodule 12 may be configured as a linked list with a consecutive memoryvalue pool that is well adapted to provide a fast and high volume dataupdating method. The linked list provides a data structure that consistsof a sequence of data records such that in each record there is a fieldthat contains a reference (the link) to the next record in the sequence.The linked list allows the parameter values in the functional moduleinternal data tables 45 to be updated by batch, instead of one by one,although individual parameter updates is certainly contemplated. Use ofbatch updating for large amounts of real time power data providesimproved performance.

The system 10 may further incorporate a time protocol for correlationand/or time stamping each single acquired data or event. In oneembodiment, the time protocol comprises the precision time protocol(PTP) defined in the IEEE 1588 standard. Other methods for timecoordination are contemplated, including other protocols such as thenetwork time protocol (NTP or Simple NTP), global positioning system(GPS), and a variety of other known or future developed time protocols.As a local Ethernet backplane, the backplane assembly 22 is able tosupport the IEEE 1588 high precision time protocol. As the data isreceived at one or more functional modules, it may be time-stamped bythe time protocol so it can be correlated in time with the time-stampeddata from other functional modules. Time stamp accuracy may be in therange of 100 ns, or more or less. In one embodiment, any of thedata/events generated in any of the multiple functional modules in thesystem 10 can be processed chronologically.

Scheduled data updates and real time data updates may be transmittedusing the producer/consumer model (see FIG. 4). For example, afunctional module 14 may publish its module description on the backplane22 during the initialization process by responding to a create assemblylocal command. Once the functional module 14 is recognized, the primarymodule 12 may then open an input and output (I/O) connection 56 betweenthe primary module and the functional module through the use of a createconnection local command. After the system initialization, during thesystem runtime, the functional module 14 may keep publishing its data onto the backplane periodically by responding to data update localcommands. If one of the other functional modules 16, 18, 20 in thesystem or a new functional module requires data from the functionalmodule 14, the other or new functional module(s) may create aninput-only connection with the functional module 14 to subscribe thedata produced by the functional module 14.

As described above, the multifunctional system 10 may be data driven andmay include multiple functional modules connected through the backplaneassembly 22. The producer/consumer model allows modules to send(produce) and receive (subscribe) data independent of the I/Oconnections 56, where the data is collected directly from themodule/backplane without the need for complicated programming. Each ofthe modules can be a data publisher or a data subscriber. During thesystem run time, the data publishers publish data to the backplane, andthe data subscribers get the data that they are interested in from thebackplane. This approach defines the data exchange between modules inthe producer, consumer scheme. System behavior is advantageously morepredictable, making data exchange easier to verify. In theproducer/consumer model, the modules are decoupled and each module isadapted to work independently. Boundary conditions are the factors thatreflect each modules status. These boundary conditions areadvantageously easier to identify and validate, and they provideinformation about each module that may simplify system maintenance.

In other cases, certain modules may be programmed to “listen” on thebackplane for data transmissions tagged as originating from othermodules, and these certain modules may then consume information in thedata transmissions when the originating module is one from whichinformation is sought.

The steps performed while practicing an exemplary embodiment of creatingthe module description 40 consistent with the embodiments describedherein are set forth in FIG. 5. The description generator tool 60 helpsa functional module firmware developer to create module descriptions.The description generator tool 60 may be developed by using MicrosoftExcel Visual Basic for Applications (VBA), although it is contemplatedthat other software may be used as well. Referring particularly to FIG.5, the first step inputs module specific information into thedescription generator tool 60 running on a PC, such as a laptop forexample, (not shown) that includes a preconfigured data entry form 70(see FIG. 6), such as a spreadsheet form, for example an Excelspreadsheet, as indicated at process block 72. In one embodiment, thespreadsheet form 70 contains two parts or sections (although notrequired); a section 74 for data table information and a section 76 forthe description generator code in VBA. It is to be appreciated that eachsection may include one or more “sheets” or “pages.” The data tablesection 74 in the spreadsheet form 70 is used by the developer to inputdetailed information about the functional module parameters and aboutthe parameters internal data table structures 44 and external data tablestructures 46. The functional module firmware developer may only need tofill the information into the data entry form 70 in the preconfiguredformat.

At process block 80, the description generator tool 60 is used togenerate program files, including but not limited to .c files (C or C++programming language files) and/or .h files (header files). At processblock 82, the program file(s) are compiled to create the moduledescription 40. The program files can be compiled by differentcompilers, which depends on the type of processor 88 in the functionalmodules. For example, if a functional module uses a DSP processor, thefunctional module developer may use the compiler for the DSP processorto generate the compiled module description. And if a functional moduleuses an ARM processor, the developer may use a specific compiler for theARM processor. Next, at process block 84, the module description 40 issaved in memory 86, such as non-volatile memory in the functionalmodule.

Once the module description 40 is generated for each module and thesystem 10 is assembled, the system can be self-organized. The stepsperformed while practicing an exemplary embodiment of self-organizingthe system 10 consistent with the embodiments described herein are setforth in FIG. 7. The first step includes assembling a system including aprimary module 12, at least one functional module 14, a backplaneassembly 22, and a power supply module 18, as indicated at process block90. Once assembled, at process block 92, power is supplied to the system10. At system initialization time, the primary module 12 initiates acreate assembly local command across the backplane 22. Next, at processblock 94, the functional module 14 sends its module description 40 tothe primary module 12. At process block 96, the description parser 50 ofthe primary module 12 uses the functional module description 40 tocreate the dynamic data table structures 42. An I/O connection 56 maythen be established at process block 98, allowing communication betweenthe primary module 12 and the functional module 14. The steps arerepeated starting at step 92 for any additional functional modules inthe system 10. Steps 92, 94, and 96 may also be repeated when a newfunctional module is added to a previously organized system 10.

As seen in FIG. 1, the previously described communication interface 28of the primary module 12 provides access to other systems and devices onthe network 100. Additional devices such as a laptop 102, a display 104,and/or a Human Machine Interface (HMI) 106, as non-limiting examples,may also reside on the network 100 and may communicate directly orindirectly with the primary module 12 or other devices on the network.The additional devices allow a user to access the external data tables47 from the primary module 12 for system data analysis.

Therefore, systems and methods that are adapted to self-organize amultifunctional power and energy control and management system byintegrating multiple backplane based modules through module descriptionswithout the need for a user to configure the system by usingconfiguration software are provided. A dynamic data structure may beincorporated to improve data access, storage and updating. It iscontemplated that the data/data structures may be time-stamped andtemporarily or permanently recorded. The time-synchronized data may thenbe made available to each module in the system for analysis.

The foregoing has been a detailed description of illustrativeembodiments of the invention. Various modifications and additions can bemade without departing from the spirit and scope thereof. Furthermore,since numerous modifications and changes will readily occur to thoseskilled in the art, it is not desired to limit the invention to theexact construction and operation shown and described. For example, anyof the various features described herein can be combined with some orall of the other features described herein according to alternateembodiments. While the preferred embodiment has been described, thedetails may be changed without departing from the invention, which isdefined by the claims.

Finally, it is expressly contemplated that any of the processes or stepsdescribed herein may be combined, eliminated, or reordered. In otherembodiments, instructions may reside in computer readable medium whereinthose instructions are executed by a processor to perform one or more ofprocesses or steps described herein. As such, it is expresslycontemplated that any of the processes or steps described herein can beimplemented as hardware, software, including program instructionsexecuting on a computer, or a combination of hardware and software.Accordingly, this description is meant to be taken only by way ofexample, and not to otherwise limit the scope of this invention.

1. A system comprising: a backplane assembly; at least one functionalmodule coupled to the backplane assembly and adapted to receive processrelated data, the at least one functional module including a uniquemodule description, the module description including information aboutdata structures and control logic of the at least one functional module;and a primary module coupled to the backplane assembly, the primarymodule including a description parser adapted to receive and interpretthe at least one module description upon self-organization of the systemand to create a dynamic data table structure.
 2. The system according toclaim 1: wherein the dynamic data table structure includes a consecutivememory value pool adapted for data accessing and uploading.
 3. Thesystem according to claim 1: further including a power supply module,the power supply module coupled to the backplane assembly and adapted toprovide power across the backplane to each module coupled to thebackplane assembly.
 4. The system according to claim 1: the primarymodule further including a logic engine adapted to operate on data inthe dynamic data table structure.
 5. The system according to claim 1:wherein the system comprises a power and energy control and managementsystem.
 6. The system according to claim 1: wherein the process relateddata includes energy related data.
 7. The system according to claim 1:wherein the dynamic data table structure includes at least one externaldata table corresponding to the at least one functional module.
 8. Thesystem according to claim 1: wherein the module description includinginformation about data structures includes information about internaldata table parameters and external data table parameters.
 9. The systemaccording to claim 1: wherein the at least one functional module isconfigured to manage its communications to and from the backplaneassembly.
 10. The system according to claim 1: wherein the dynamic datatable structure includes at least one internal data table correspondingto the at least one functional module.
 11. The system according to claim10: wherein the at least one functional module further includes at leastone internal data table that corresponds to the at least one internaldata table in the dynamic data table structure.
 12. A power and energycontrol and management system comprising: a backplane assembly; afunctional module coupled to the backplane assembly, the functionalmodule including at least one internal data table and a unique moduledescription, the unique module description including information aboutthe internal data table parameters and external data table parameters ofthe functional module; and a primary module coupled to the backplaneassembly, the primary module including a description parser adapted toreceive and interpret the internal data table parameters and theexternal data table parameters of the functional module uponself-organization of the system, and to create a dynamic data tablestructure including at least one external data table, the at least oneexternal data table being dynamically created based on the external datatable structures of the functional module.
 13. The system according toclaim 12: wherein the primary module uses the at least one external datatable to exchange data with at least one device that is not coupled tothe backplane assembly.
 14. The system according to claim 12: whereinself-organization of the system is accomplished without system userintervention.
 15. The system according to claim 12: wherein thedescription parser is further adapted to create a parameter list basedon the unique module description of the functional module.
 16. Thesystem according to claim 15: the primary module further includingcontrol logic, and wherein parameters in the parameter list are adaptedto be used as inputs to the control logic.
 17. The system according toclaim 12: further including additional functional modules, thefunctional module adapted to exchange data with the additionalfunctional modules without intervention from the primary module.
 18. Thesystem according to claim 17: wherein when real-time data is received atthe functional module, the real-time data is time-stamped by a timeprotocol so the time-stamped real-time data can be correlated in timewith time-stamped real-time data from the additional other functionalmodules.
 19. A method of self-organizing a power and energy control andmanagement system, the method comprising: inputting into a descriptiongenerator tool information about a functional module, the informationcomprising information about internal data table structures and externaldata table structures; creating a module description specific to thefunctional module by compiling the information input into thedescription generator tool; saving the module description in memory inthe functional module; and self-organizing the system by i) sending themodule description across a backplane assembly to a primary module, theprimary module adapted to receive the module description; ii) using adescription parser to create dynamic data table structures based on themodule description; and iii) establishing an I/O connection between theprimary module and the functional module.
 20. The method systemaccording to claim 19: wherein self-organizing the system isaccomplished without system user intervention.